home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19950329-19950528
/
000262_news@columbia.edu_Thu Apr 27 06:35:40 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA13611
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Thu, 27 Apr 1995 19:44:19 -0400
Received: by apakabar.cc.columbia.edu id AA00783
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Thu, 27 Apr 1995 19:44:17 -0400
Path: news.columbia.edu!sol.ctr.columbia.edu!howland.reston.ans.net!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Using OS/2 C-Kermit 191 with SLIP.EXE
Message-Id: <1995Apr27.123541.48939@cc.usu.edu>
Date: 27 Apr 95 12:35:40 MDT
References: <3nn3ib$dut@vixen.cso.uiuc.edu>
Distribution: usa
Organization: Utah State University
Lines: 38
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <3nn3ib$dut@vixen.cso.uiuc.edu>, adam@symcom.math.uiuc.edu (Adam H. Lewenberg) writes:
> I am a little confused by some of the explanation in the "Updates to
> Using C-Kermit" that comes with OS/2 C-Kermit 5A(191). In particular,
> the section titled "Using C-Kermit to make SLIP connections". From
> that section:
>
> "Note that C-Kermit should not be used as part of an attachment
> script, which is started by the SLIP driver itself, but should be
> run as a separate command _after_ [emphasis mine] the SLIP driver
> is started. Should scripting be required, you can use Kermit
> scripts [..] to perform the same tasks as an attachment script."
>
>
> Doen't this paragraph contradict itself? First it says not to use
> C-Kermit as part of an attachment script, but then it says you CAN use
> C-Kermit as an attachment script. What exactly is meant by this
> paragraph?
>
>
> A further but related question: let's say I want to use C-Kermit to
> dial-up a slip server, and then start SLIP.EXE that comes with OS/2
> Warp. How does one do this? In particular, what command-line options
> should be given to SLIP.EXE? When should SLIP.EXE be started, before
> reaching the server or only after starting the remote slip connection?
> Maybe someone can give a careful explanation of how all the pieces fit
-----------
No need to be careful in the explanation: it's obvious in practice(tm).
Initially your remote terminal server agent is NOT speaking SLIP, and it
requires human chatter to login etc. Use Kermit for that task. Then you
start SLIP on it and escape back to the local PC to start SLIP locally.
After SLIP is running happily locally and remotely start Kermit to run over
the internal TCP/IP stack.
The difference in approach is because part of the time SLIP is not
running. And during that part Kermit provides the link between your fingers
and the remote machinery.
If you have a variation of this then just "let your fingers do the
walking" the first time and then turn that much into a script.
Joe D.